Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor how to determine if a field is metafield (#57378) #57771

Merged

Conversation

mayya-sharipova
Copy link
Contributor

Before to determine if a field is meta-field, a static method of MapperService
isMetadataField was used. This method was using an outdated static list
of meta-fields.

This PR instead changes this method to the instance method that
is also aware of meta-fields in all registered plugins.

Related #38373, #41656
Closes #24422

Before to determine if a field is meta-field, a static method of MapperService
isMetadataField was used. This method was using an outdated static list
of meta-fields.

This PR instead changes this method to the instance method that
is also aware of meta-fields in all registered plugins.

Related elastic#38373, elastic#41656
Closes elastic#24422
@mayya-sharipova
Copy link
Contributor Author

backport, opened a PR just to make sure CI passes

@mayya-sharipova mayya-sharipova added backport v7.9.0 :Search/Search Search-related issues that do not fall into other categories labels Jun 5, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Search)

@elasticmachine elasticmachine added the Team:Search Meta label for search team label Jun 5, 2020
@mayya-sharipova mayya-sharipova merged commit 70e63a3 into elastic:7.x Jun 8, 2020
@mayya-sharipova mayya-sharipova deleted the metafield-refactoring-7.x branch June 8, 2020 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team v7.9.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants